Open topic with navigation

KMF Integration Service - Manual Upgrade: Upgrading Kony MobileFabric Integration Service > Tomcat > Upgrading Tomcat Manually 6.0.x to 6.5.x

Upgrade Tomcat Manually from 6.x to 6.5.x

This section provides you the steps to upgrade Kony MobileFabric Integration Service manually from 6.x to 6.5.x (Tomcat).

Prerequisites

The following table displays the prerequisites for upgrading Kony MobileFabric Integration Service.

Refer to http://community.kony.com/downloads/manual to download the following artifacts:

Artifacts Type Purpose
Resepective Database Upgrade Scripts Database scripts To setup the required schema
  • admin.war
  • middleware.war
  • appdownload.war
  • metrics.ear (applicable only for metrics)

    (Advantages)

 WAR and EAR files To be deployed to Application Server
  • middleware-bootconfig.tar
  • libraries-MIDDLEWARE-GA-<6.0.x>.tar
TAR files  
JAR files  

Backup

To backup files, follow these steps: 

  1. Stop JMS and Tomcat middleware server.

  2. Take a backup of the following files from your current server installation location.
    1.  .WAR files - These files are available at <install-location>\install\webapps .
      • middleware.war
      • admin.war
      • appdownload.war
      • metrics.ear from <install-location>\jboss62_jms\standalone\deployments (applicable only for metrics).
    2. middleware-bootconfig directory from <install-location>\install\middleware
    3. middleware libraries (.JAR files) - The files are located at \<install-location>\install\lib\middleware.
    4. After taking the backup, delete all the above files.

Execute Database Scripts

  1. Execute the database upgrade scripts from http://community.kony.com/downloads/manual.

    2. Note: Run the scripts in the given order. Replace the name of the konyadmin and konyreports schema name to your respective schemas.

Add Management Related Entries in Admin DB (Applicable Only For MobileFabric)

  1. Open mobilefabric_configuration table from your admin database.
  2. Add the following entries under the data column:
  3. Take a backup of the following files and delete them.
    1. management_server_host_name - assign your host name as prop_value.
    2. managment_server_port - assign your management port number as prop_value

Add New and Update Existing Property Files

  1. Extract the middleware-bootconfig.tar to the following location <install-location>\install\middleware.
  2. Retain the properties of admin-log4j.propertiesand deployment-config.properties under middleware-bootconfig\admin folder from the previous versions.
  3. In middleware.properties and middleware-log4j.properties in middleware-bootconfig folder, retain all the existing properties from the previous versions.
  4. Copy the appregistry folder under the middleware-bootconfig of previous version to the new middleware-bootconfig folder.
  5. Open middleware-log4j.properties and edit the below paths for device-payload.log and datasource-payload.log as your requirement.
    log4j.appender.DEVICE.File=${middleware.home}\..\logs\middleware\device-payload.log
log4j.appender.DATASOURCE.File=${middleware.home}\..\logs\middleware\datasource-payload.log
  6. If metrics is not used, open middleware.properties in the middleware-bootconfig folder from <install-location>\install\middleware and mark the property under Metrics Topic Configuration as false

    metrics.logging=false

    Note: This property was introduced in 6.0.3.x.GA version of middleware. This property is used to enables the metrics. Request and Session data is captured in the database if this property is set to true.

    Note: If we set metrics.logging property to false, call the kony.license.disableMetricReporting() API in app init to disable “Maximum Offline Sessions Exceeded” alert.

  7. Mark the property metrics.logging =true (applicable only for metrics).

  8. Retain the properties of metrics-log4j.properties in middlware-bootconfig\admin folder, and serverconsole.properties in middleware-bootconfig folder from the previous versions.

Deploy Latest Artifacts

  1. Copy the latest admin.war, middleware.war and appdownload.war to <install_location>\install\webapps.

  2. Extract and copy the JARs from libraries-MIDDLEWARE-GA-<version>.tar to <install-location>\install\lib\middleware.

  3. If you are using thin client application, add the thin client jars to <install-location>\install\lib\tc , (create the folder tc under lib if it does not exist).

  4. Copy the metrics.ear to <install-location>\jboss62_jms\standalone\deployments (applicable only for metrics).

Verification

Verify the upgrade process by logging into the console and look for Server Version and Health Check. Use version.html for verification.

To verify the upgrade process, follow these steps:

  1. Start JMS server by clicking startjboss.bat from <install-location>\jboss62_jms\bin.

  2. Start tomcat middleware server by clicking startup.bat from <install-location>\tomcat\instance\bin.

  3. To verify the middleware version, navigate to the URL http://ipaddress:port\middleware\version.html and look for server version.

  4. Navigate to Settings and click Health Check and look for Report DB, Admin DB and Reporting.

  5. Navigate to Settings and click Configuration and verify the version.

Copyright © 2013 Kony, Inc. All rights reserved.

Open topic with navigation